Skip to content

ci: let a manually triggered run actually deploy - #54

Merged
leinss merged 1 commit into
releasefrom
feature/deploy-gate
Aug 27, 2026
Merged

ci: let a manually triggered run actually deploy#54
leinss merged 1 commit into
releasefrom
feature/deploy-gate

Conversation

@leinss

@leinss leinss commented Aug 27, 2026

Copy link
Copy Markdown
Owner

The deploy job was gated on github.event_name == 'push'. A manual run therefore built and then skipped the deploy, so the manual trigger could not redeploy, which is the only reason it exists. Measured on a dispatch run: Build & Check: success, Deploy to GitHub Pages: skipped.

Changes

  • Gate the deploy job on github.event_name != 'pull_request' instead of == 'push'.

A pull request must still build without publishing. Every other trigger deploys, so a trigger added later cannot silently produce a build-only run.

Test plan

  • The PR run builds and skips the deploy job.
  • After merge, a workflow_dispatch run reaches Deploy to GitHub Pages: success.
  • The site still serves after that manual deploy.

The deploy job was gated on `github.event_name == 'push'`. A manual run
therefore built and then skipped the deploy, so the manual trigger could
not redeploy, which is the only reason it exists.

Gate on `!= 'pull_request'` instead. A pull request must still build
without publishing; every other trigger deploys, so adding a trigger
above cannot silently produce a build-only run again.
@leinss
leinss merged commit 4c28e14 into release Aug 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant